Push Channels
Epicenter's push channels use CometD and the BAYEUX protocol under the hood.
Forio takes care of sending out messages over push channels. As a developer of Epicenter apps, you need to enable channels to receive messages.
For a detailed description of how push channels are implemented in Epicenter, read the push channel reference pages.
Push channel messages are sent by the Epicenter platform for entity-related events. To send simulation-related messages to your users, use the Chat adapter.
Push category
The push category is a property of an Epicenter push channel. It defines the category of the notifications sent to the channel.
The push category is implemented in the JS libraries with the PUSH_CATEGORY enum.
Path
A push channel is defined by its scope and an additional property, identifying the push category.
The push channel's path is constructed as /{scope boundary}/{scope key}/{push category}.
Channel scope
The scope and push category together comprise a channel scope, which defines what the messages on the channel are related to. For example, when users subscribe to a world-scoped channel with a VAULT category, they get vault-related messages about the world referenced by the scope key.
Enabling push channels
In projects with a Silent phylogeny, to enable push-channel notifications for specific entities set allowChannel to true on those entities.
For some entities, you must set allowChannel to true on the project level.
Subscriber presence
The channels monitor subscribers' presence. The facilitators can use this information to regroup participants and form new worlds depending on who is online.
For more details, read about the Presence adapter.